Crop density map using row sensors

ABSTRACT

A harvester has a stool width sensor that senses stool width of a crop stool. A position sensor senses a position of the harvester, and a map generator generates a map based on the sensed stool width and the sensed position.

FILED OF THE DESCRIPTION

The present description relates to ratoon crops. More specifically, the present description relates to generating a map for a ratoon crop.

BACKGROUND

Sugarcane is a tropical grass. Therefore, it is a ratoon crop. As one example, some ratoon crops grow by having new shoots sprout from a plant base so that it can be harvested multiple times, before it is re-planted.

When the sugarcane is planted, or re-planted, portions of mature cane stalk are laid in a furrow in the soil. These portions of stalk are referred to as setts, and they are then covered with soil. Multiple stalks grow from each sett. For instance, in some cases, up to twelve separate stalks grow from one sett. This group of stalks, that grows from a single sett, is referred to as the stool of sugarcane.

Over time, the yield of a given sugarcane field will decrease. This can occur for a variety of reasons. For instance, sugarcane is often harvested using mechanical harvesters. In addition, there are often post-harvesting mechanical operations in which mechanical equipment drives over the harvested sugarcane field. All of these types of operations can cause damage to the field. For example, the setts can be damaged, and the roots of a given stool can be torn from the ground. The yield of a field can decrease over time for other reasons as well.

The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.

SUMMARY

A harvester has a stool width sensor that senses stool width of a crop stool. A position sensor senses a position of the harvester, and a map generator generates a map based on the sensed stool width and the sensed position.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one example of a ratoon crop harvester.

FIG. 2 is a flow diagram illustrating one embodiment of the operation of the harvester shown in FIG. 1 in generating a stool width map.

FIGS. 3 and 4 are pictorial illustrations showing one embodiment of a stool width sensor.

FIG. 5 is a block diagram of the harvester deployed in one example of a remote server configuration.

FIGS. 6-9 are examples of mobile devices.

FIG. 10 is a block diagram of one exemplary computing environment.

DETAILED DESCRIPTION

As discussed in the background portion, sugarcane plants in a sugarcane field can become damaged over time, which results in the overall yield of the sugarcane field decreasing over time. In some cases, sugarcane is harvested several times before the overall yield decreases to a point where the farmer re-plants the entire field.

Replanting the entire field is quite costly and time consuming. It is less costly to replant only damaged or low yield portions of the field. However, identifying such damaged or low yield portions can be difficult. This is because, while the sugarcane setts are planted in rows, the rows, at harvest time, are often rough and irregular in their shape and spacing. It is therefore difficult to obtain an accurate yield map for a sugarcane field. Without a yield map, it is difficult to locate the low yield portions in the field. Thus, the farmer often simply waits until the overall yield for the entire field decreases to a point where it makes sense to replant the entire field.

FIG. 1 is a block diagram of one illustrative ratoon crop harvester (such as a sugarcane harvester) that generates a stool width map that allows the farmer to identify locations in the sugarcane field that are providing weak production. This enables the sugarcane farmer to identify portions of the field that are good candidates for renewal without renewing or re-planting the entire field. Identifying these renewal candidate areas, and renewing only those areas instead of the entire field, can maintain the overall yield of a sugarcane field, yet reduce the relative number of re-plantings that are performed to maintain that yield. It will also be noted that sugarcane is but one example of a ratoon crop. While the present discussion proceeds with respect to the ratoon crop being sugarcane, it could be other crops as well. For instance, in some environments, rice is grown as a ratoon crop.

FIG. 1 thus shows that ratoon crop harvester 100 illustratively includes a stool width sensor 102, and a position sensing component 104. It can also include a mass flow sensor 103 as well. Harvester 100 also illustratively includes map generator 106 (that generates map 107). Harvester 100 can also include processor 108, display device 110, data store 112 and communication component 114. FIG. 1 shows that, in one embodiment, communication component 114 can communicate with a remote display or reporting device 116, other machines 117, with a remote analysis system 118, with remote storage 120, with third-parties 122, or with other items 124.

Before describing the overall operation of harvester 100 in generating map 107 in detail, a brief overview will be provided. As harvester 100 is traveling through the sugarcane field, stool width sensors 102 sense the width of the stool passing between the crop dividers on harvester 100. Mass flow sensor 103 senses the mass flow rate of harvested crop through harvester 100. Position sensing component 104 senses the position and heading of harvester 100 within the field, and map generator 106 illustratively generates map 107 by correlating the sensed stool width (generated by sensors 102) with the position (generated by component 104) and possibly other inputs.

Map 107 can be a stool width map 109 that maps stool width across the field. This can be generated based on the sensed stool width and the sensed machine position.

Map 107 can also be a yield map 111 that incorporates the inputs from mass flow sensor 103, stool width sensors 102 and position sensing component 104. It can be difficult to map yield based only on an input from mass flow sensor 103 and position sensing component 104. This is because, by the time sensor 103 outputs a mass flow rate signal, harvester 100 has moved from the position where the crop responsible for the signal was harvested. However, by incorporating the stool width sensed by sensors 102, map generator 106 can more accurately estimate the location corresponding to a given mass flow rate. If the mass flow rate is higher, this more likely corresponds to a geographic location where the stool was wider, and vice versa.

In another embodiment, the map 107 can be a crop position map 113. The crop position map 113 can be used, for instance, to control traffic patterns of machines on the field after harvesting. Cane is often cut very close to the ground, and the straw generated from harvesting often covers the field as well. This can make it difficult to see where the rows are before the plants begin to sprout again. It may take several weeks for the plants to sprout. During that time, other machines may be traveling on the field, such as to apply weed control materials, pesticides, or fertilizer, etc. Thus the crop position map 113 can be used to avoid driving on, and damaging, the plants.

The crop position can be calculated by map generator 106 based on a number of things. For instance, map generator 106 can consider the position of crop dividers 162 and 164 relative to the machine (such as from the known machine geometry and the current machine heading) and the crop position relative to the crop dividers 162 and 164 (such as from stool width sensors 102). Using these things, map generator 106 can generate a crop position map 113 that can be used in a variety of different ways, some of which are discussed above.

Map 107 can be stored locally in data store 112, or it can be displayed locally on display device 110. It can include a variety of information as mentioned above, as well as the crop density (indicated, for example, by the stool width) mapped against the various locations within the field from which it was harvested. This is indicated by block 126. It can include a density variance metric that shows how the crop density (or stool width) varies at different locations in the field. This is indicated by block 128. It can identify gap locations (such as where the stool is very thin or non-existent) within the field. This is indicated by block 130. It can provide a relative yield map that indicates a relative yield (which can be calculated or estimated from the sensed stool width) at various locations in the field. This is indicated by block 132. It can also identify renewal candidate areas 134 that indicate where the stool is relatively thin, within the field, and identify these areas as candidate areas for re-planting. Of course, the map 107 can indicate other items 136 as well.

FIG. 2 is a flow diagram illustrating one embodiment of the operation of harvester 100 in generating map 107, in more detail. The operator first begins harvesting, using harvester 100. This is indicated by block 140 in FIG. 2. Stool width sensors 102 sense the stool width, mass flow sensor 103 senses mass flow through harvester 100, and position sensing component 104 senses the machine position within the field, as the machine moves through the field. This is indicated by block 142.

In one embodiment, the stool width sensors 102 are deflection sensors, as indicated by block 144. They can be other sensors as well, such as ultrasonic sensors 146, optical sensors 148, microwave sensors 150 or other sensors 152. Position sensing component 104 can be a global position system (GPS) sensor 154, a dead reckoning sensor 156, or a wide variety of other sensors 158.

Before continuing with the description of FIG. 2, a more detailed embodiment of stool width sensors 102 will be described. FIGS. 3 and 4 show one embodiment in which stool width sensors 102 are deflection sensors 144. FIG. 3 shows a pictorial front view of harvester 100. It can be seen that harvester 100 illustratively includes an operator's compartment 160 and a pair of crop dividers 162 and 164. It will be noted that in other embodiments there may be a different number of crop dividers. The direction of travel of harvester 100 is illustratively out of the page of FIG. 3. FIG. 4 shows an enlarged view of a front portion of the harvester 100 shown in FIG. 3. The direction of travel is indicated by arrow 161 in FIG. 4. FIGS. 3 and 4 will now be described in conjunction with one another

FIGS. 3 and 4 show that harvester 100 illustratively includes a set of base cutters 166 and 168 as well as a knock down roller 170. FIG. 3 shows a stool, generally indicated by arrow 172. FIGS. 3 and 4 also show a set of deflectable arms 174 and 176. They are illustratively biased to a position where they come together, or slightly overlap one another, at their end portions 178 and 180, respectively. Therefore, as the machine moves toward stool 172, the stalks that form the stool deflect the deflectable arms 174 and 176 backwards, in a direction generally toward knockdown roller 170 (or into the page of FIGS. 3 and 4). A set of sensors 102, such as strain gauge sensors, potentiometers, Hall effect sensors or other sensors, sense the extent to which deflectable arms 174 and 176 deflect, as they engage the stool 172. Therefore, if stool 172 has a relatively large number of stalks (and thus a relatively large stool width), then both of the deflectable arms 174 and 176 will deflect rearwardly by a relatively large distance. However, if stool 172 only has a small number of stalks (and thus a relatively small stool width), then deflectable arms 174 and 176 will only deflect a relatively small distance.

Continuing on with the description of FIG. 2, map generator 106 illustratively receives the stool width sensor output signal from sensors 102, the mass flow signal from sensor 103, and the position signal from position sensing component 104. Map generator 106 then illustratively correlates the measured or sensed stool width to the location of harvester 100, within the field, as output by component 104. This is indicated by block 182 in the flow diagram of FIG. 2.

Based upon the correlation of the stool width and the location, map generator 106 illustratively generates map 107. Generating the map 107 is indicated by block 184 in FIG. 2. The map 107 can be generated based on other inputs as well, such as the mass flow. Map generator 106 outputs map 107, as indicated by block 186.

As briefly mentioned above, map 107 can be output to a wide variety of different places, and it can be used in a wide variety of different ways. For instance, it can be displayed locally on display device 110 of machine 100, or it can be displayed remotely at a remote display device or report generator 116. Displaying either locally or remotely, or generating reports from the information on map 107, is indicated by block 188 in the flow diagram of FIG. 2.

It can also be downloaded to other machines as a crop position map so the other machines can avoid driving over, and hence damaging, the crop. This is indicated by block 189 in FIG. 2.

Map 107 can also be subjected to further analysis. For instance, it can be stored in data store 112 on machine 100 and analyzed by processor 108, in order to obtain the crop yield 111, crop position 113, mapped crop density 126, the density variants 128, the gap locations 130, the relative yield 132, the renewal candidate areas 134 or other information 136. Of course, it can also be provided to remote analysis system 118, where that type of analysis can be performed remotely. Outputting the map 107 for remote or local analysis is indicated by block 190 in the flow diagram of FIG. 2.

It can be stored locally on data store 112 or output to remote storage 120. Outputting it for either remote or local storage is indicated by block 192.

It can also be output to third-parties 122. This is indicated by block 194 in FIG. 2. By way of example, it can be output to an agronomist for further analysis. It can also be output to a fertilizer company or a pesticide company. It can be output to a machine manufacturer company for further analysis, or storage, or for historical analysis to indicate where gaps evolve over the years. It can be output to a farm manager, various other vendors, manufacturers, or other companies, so that they can identify the needs of this particular farmer (such as how many additional setts are needed, how much additional fertilizer is needed, etc.). Of course, the map can be used in other ways as well, and this is indicated by block 196 in the flow diagram of FIG. 2.

It can thus be seen that the system shown in FIG. 1 can be used to generate the map 107 or a wide variety of other information, such as, yield 111, crop position 113, mapped crop density 126 or other information. This information can be used by a sugarcane farmer to accurately identify the parts of a sugarcane field that need to be re-planted. The farmer can thus maintain the overall yield of the given field, without needing to replant the entire field as often as would otherwise be needed.

The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.

Also, a number of user interface displays have been discussed. They can take a wide variety of different forms and can have a wide variety of different user actuatable input mechanisms disposed thereon. For instance, the user actuatable input mechanisms can be text boxes, check boxes, icons, links, drop-down menus, search boxes, etc. They can also be actuated in a wide variety of different ways. For instance, they can be actuated using a point and click device (such as a track ball or mouse). They can be actuated using hardware buttons, switches, a joystick or keyboard, thumb switches or thumb pads, etc. They can also be actuated using a virtual keyboard or other virtual actuators. In addition, where the screen on which they are displayed is a touch sensitive screen, they can be actuated using touch gestures. Also, where the device that displays them has speech recognition components, they can be actuated using speech commands.

A number of data stores have also been discussed. It will be noted they can each be broken into multiple data stores. All can be local to the systems accessing them, all can be remote, or some can be local while others are remote. All of these configurations are contemplated herein.

Also, the figures show a number of blocks with functionality ascribed to each block. It will be noted that fewer blocks can be used so the functionality is performed by fewer components. Also, more blocks can be used with the functionality distributed among more components.

It will also be noted that the information on map 107 can be output to the cloud.

FIG. 5 is a block diagram of harvester 100, shown in FIG. 1, except that it communicates with elements in a remote server architecture 500. In an example embodiment, remote server architecture 500 can provide computation, software, data access, and storage services that do not require end-user knowledge of the physical location or configuration of the system that delivers the services. In various embodiments, remote servers can deliver the services over a wide area network, such as the internet, using appropriate protocols. For instance, remote servers can deliver applications over a wide area network and they can be accessed through a web browser or any other computing component. Software or components shown in FIG. 1 as well as the corresponding data, can be stored on servers at a remote location. The computing resources in a remote server environment can be consolidated at a remote data center location or they can be dispersed. Remote server infrastructures can deliver services through shared data centers, even though they appear as a single point of access for the user. Thus, the components and functions described herein can be provided from a remote server at a remote location using a remote server architecture. Alternatively, they can be provided from a conventional server, or they can be installed on client devices directly, or in other ways.

In the embodiment shown in FIG. 5, some items are similar to those shown in FIG. 1 and they are similarly numbered. FIG. 5 specifically shows that map generator 106, systems 116 and 118 and storage 120 can be located at a remote server location 502. Therefore, harvester 100 accesses those systems through remote server location 502.

FIG. 5 also depicts another embodiment of a remote server architecture. FIG. 5 shows that it is also contemplated that some elements of FIG. 1 are disposed at remote server location 502 while others are not. By way of example, remote storage 120 or third party system 122 can be disposed at a location separate from location 502, and accessed through the remote server at location 502. Regardless of where they are located, they can be accessed directly by harvester 100, through a network (either a wide area network or a local area network), they can be hosted at a remote site by a service, or they can be provided as a service, or accessed by a connection service that resides in a remote location. Also, the data can be stored in substantially any location and intermittently accessed by, or forwarded to, interested parties. For instance, physical carriers can be used instead of, or in addition to, electromagnetic wave carriers. In such an embodiment, where cell coverage is poor or nonexistent, another mobile machine (such as a fuel truck) can have an automated information collection system. As the harvester comes close to the fuel truck for fueling, the system automatically collects the information from the harvester using any type of ad-hoc wireless connection. The collected information can then be forwarded to the main network as the fuel truck reaches a location where there is cellular coverage (or other wireless coverage). For instance, the fuel truck may enter a covered location when traveling to fuel other machines or when at a main fuel storage location. All of these architectures are contemplated herein. Further, the information can be stored on the harvester until the harvester enters a covered location. The harvester, itself, can then send the information to the main network.

It will also be noted that the elements of FIG. 1, or portions of them, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.

FIG. 6 is a simplified block diagram of one illustrative embodiment of a handheld or mobile computing device that can be used as a user's or client's hand held device 16, in which the present system (or parts of it) can be deployed. For instance, a mobile device can be deployed in the operator compartment of harvester 100 for use in generating, processing, or displaying the stool width and position data. FIGS. 7-9 are examples of handheld or mobile devices.

FIG. 6 provides a general block diagram of the components of a client device 16 that can run some components shown in FIG. 1, that interacts with them, or both. In the device 16, a communications link 13 is provided that allows the handheld device to communicate with other computing devices and under some embodiments provides a channel for receiving information automatically, such as by scanning. Examples of communications link 13 include allowing communication though one or more communication protocols, such as wireless services used to provide cellular access to a network, as well as protocols that provide local wireless connections to networks.

Under other embodiments, applications can be received on a removable Secure Digital (SD) card that is connected to an interface 15. Interface 15 and communication links 13 communicate with a processor 17 (which can also embody processor 108 from FIG. 1) along a bus 19 that is also connected to memory 21 and input/output (I/O) components 23, as well as clock 25 and location system 27.

I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, optical sensors, microphones, touch screens, proximity sensors, accelerometers, orientation sensors and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.

Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Processor 17 can be activated by other components to facilitate their functionality as well.

FIG. 7 shows one embodiment in which device 16 is a tablet computer 600. In FIG. 7, computer 600 is shown with user interface display screen 602. Screen 602 can be a touch screen or a pen-enabled interface that receives inputs from a pen or stylus. It can also use an on-screen virtual keyboard. Of course, it might also be attached to a keyboard or other user input device through a suitable attachment mechanism, such as a wireless link or USB port, for instance. Computer 600 can also illustratively receive voice inputs as well.

FIG. 8 provides an additional example of devices 16 that can be used, although others can be used as well. In FIG. 8, a feature phone, smart phone or mobile phone 45 is provided as the device 16. Phone 45 includes a set of keypads 47 for dialing phone numbers, a display 49 capable of displaying images including application images, icons, web pages, photographs, and video, and control buttons 51 for selecting items shown on the display. The phone includes an antenna 53 for receiving cellular phone signals. In some embodiments, phone 45 also includes a Secure Digital (SD) card slot 55 that accepts a SD card 57.

FIG. 9 is similar to FIG. 8 except that the phone is a smart phone 71. Smart phone 71 has a touch sensitive display 73 that displays icons or tiles or other user input mechanisms 75. Mechanisms 75 can be used by a user to run applications, make calls, perform data transfer operations, etc. In general, smart phone 71 is built on a mobile operating system and offers more advanced computing capability and connectivity than a feature phone.

Note that other forms of the devices 16 are possible.

FIG. 10 is one embodiment of a computing environment in which elements of FIG. 1, or parts of it, (for example) can be deployed. With reference to FIG. 10, an exemplary system for implementing some embodiments includes a general-purpose computing device in the form of a computer 810. Components of computer 810 may include, but are not limited to, a processing unit 820 (which can comprise processor 108), a system memory 830, and a system bus 821 that couples various system components including the system memory to the processing unit 820. The system bus 821 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. Memory and programs described with respect to FIG. 1 can be deployed in corresponding portions of FIG. 10.

Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media may embody computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.

The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation, FIG. 10 illustrates operating system 834, application programs 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only, FIG. 10 illustrates a hard disk drive 841 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 851, nonvolatile magnetic disk 852, an optical disk drive 855, and nonvolatile optical disk 856. The hard disk drive 841 is typically connected to the system bus 821 through a non-removable memory interface such as interface 840, and magnetic disk drive 851 and optical disk drive 855 are typically connected to the system bus 821 by a removable memory interface, such as interface 850.

Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (e.g., ASICs), Program-specific Standard Products (e.g., ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

The drives and their associated computer storage media discussed above and illustrated in FIG. 10, provide storage of computer readable instructions, data structures, program modules and other data for the computer 810. In FIG. 10, for example, hard disk drive 841 is illustrated as storing operating system 844, application programs 845, other program modules 846, and program data 847. Note that these components can either be the same as or different from operating system 834, application programs 835, other program modules 836, and program data 837.

A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures. A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logical connections (such as a local area network—LAN, or wide area network WAN) to one or more remote computers, such as a remote computer 880.

When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. In a networked environment, program modules may be stored in a remote memory storage device. FIG. 10 illustrates, for example, that remote application programs 885 can reside on remote computer 880.

It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. 

What is claimed:
 1. A sugarcane harvester, comprising: a stool width sensor that senses a width of a sugarcane stool during harvesting when a width sensing component contacts the sugarcane stool, and provides a width signal indicative of the sensed stool width; a position sensing component that senses a position of the harvester and provides a position signal indicative of the sensed position; and a map generator coupled to the stool width sensor and the position sensing component and generates a map based on the sensed stool width and the sensed position.
 2. The sugarcane harvester of claim 1 and further comprising: a mass flow sensor that senses mass flow of sugarcane through the harvester and provides a mass flow signal indicative of the sensed mass flow.
 3. The sugarcane harvester of claim 2 wherein the map generator generates the map based on the sensed mass flow.
 4. The sugarcane harvester of claim 3 wherein the map generator correlates the sensed stool width with the sensed mass flow and the sensed position to generate a crop position map indicative of a position of sugarcane plants in the sugarcane field.
 5. The sugarcane harvester of claim 1 and further comprising: a communication component that receives the map and communicates it to a remote system.
 6. The sugarcane harvester of claim 1 wherein the map generator correlates the sensed stool width to the sensed position at locations throughout a sugarcane field.
 7. The sugarcane harvester of claim 6 wherein the map generator generates the map as a stool width map to indicate stool width throughout the sugarcane field.
 8. The sugarcane harvester of claim 6 wherein the map generator calculates crop density from the sensed stool width and generates the map to indicate the crop density throughout the sugarcane field.
 9. The sugarcane harvester of claim 8 wherein the map generator generates the map to indicate crop density variance throughout the sugarcane field.
 10. The sugarcane harvester of claim 6 wherein the map generator generates the map to show locations of crop gaps in the sugarcane field.
 11. The sugarcane harvester of claim 10 wherein the map generator generates the map to identify renewal candidate areas in the sugarcane field based on the crop gaps.
 12. The sugarcane harvester of claim 6 wherein the map generator calculates estimated yield based on the sensed stool width and generates the map to show relative yield throughout the sugarcane field.
 13. The sugarcane harvester of claim 1 wherein the stool width sensor comprises: a deflection sensor that deflects to a magnitude that varies as the stool width varies.
 14. The sugarcane harvester of claim 1 wherein the stool width sensor comprises one of a group consisting of: an optical sensor; an ultrasound sensor; and a microwave sensor.
 15. A method, comprising: receiving a stool width signal, from a stool width sensing component of a harvester, wherein the signal is indicative of a sensed stool width, as a harvester travels over a ratoon crop field and the stool width sensing component contacts a stool within the ratoon crop field; receiving a position signal indicative of a geographical location of the harvester as the harvester travels over the ratoon crop field; and generating a stool width map indicative of the sensed stool width at locations in the ratoon crop field, based on the stool width signal and the position signal.
 16. The method of claim 15 and further comprising: receiving a mass flow signal indicative of a mass flow of ratoon crop through the harvester; and generating a crop position map based on the stool width signal, the position signal and the mass flow signal.
 17. The method of claim 15 and further comprising: sensing the sensed stool width and generating the stool width signal.
 18. The method of claim 17 and further comprising: sensing the geographical location and generating the position signal.
 19. The method of claim 15 wherein generating the stool width map comprises: identifying crop gap locations in the ratoon crop field.
 20. The method of claim 15 wherein generating the stool width map comprises: calculating renewal candidate areas in the ratoon crop field based on a size of crop gaps in the ratoon crop field; and identifying the renewal candidate areas on the stool width map.
 21. The method of claim 15 and further comprising: sending the stool width map to a remote analysis system.
 22. A computer readable storage medium storing computer executable instructions which, when executed by a computer, cause the computer to perform a method comprising: receiving a stool width signal indicative of a sensed stool width when a width sensing component contacts the stool of a ratoon crop, as a harvester travels over a ratoon crop field; receiving a position signal indicative of a geographical location of the harvester as the harvester travels over the ratoon crop field; and generating a stool width map indicative of the sensed stool width at locations in the ratoon crop field, based on the stool width signal and the position signal.
 23. The computer readable storage medium of claim 22, and further comprising: receiving a mass flow signal indicative of a mass flow of ratoon crop through the harvester; and generating a crop position map based on the stool width signal, the position signal and the mass flow signal. 